-
Notifications
You must be signed in to change notification settings - Fork 593
Fix deprecated kustomization fields #1637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Fix deprecated kustomization fields #1637
Conversation
Welcome @shibataka000! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: shibataka000 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @shibataka000. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Is this a bug fix or adding new feature?
Chore.
What is this PR about? / Why do we need it?
Fix deprecated kustomization fields.
bases
withresources
as the former was deprecated since kustomize v2.1.0.patchesStrategicMerge
withpatches
as the former was deprecated since kustomize v5.0.0.What testing is done?
I ensured that the
kustomize build
command generates the same manifests as before.